User-Centred Requirements Handbook |
This section provides descriptions of each of the methods that may be used to support relevant stages of the user requirements specification framework. The material draws principally from the RESPECT Methods deliverable D3.1 (Kirakowski and Vereker, 1996).
Each method contains the following headings:
_ What Is The Method, And When Can It Be Used?
This provides a summary of what happens when the method is applied, and an indication of when it can be used.
_ Typical Application Areas
This describes the kinds of systems (e.g. a software package) or application areas (e.g. office systems) in which the method might be applied.
_ Benefits and Limitations
First the benefits are listed and then the limitations. When a method is employed it must be ensured that each limitation is either not relevant or has been catered for.
_ What you need
A description is given of the resources required to carry out the method in terms of people and resources such as equipment, rooms, etc.
_ Process
The key activities that should be carried are listed in the order they are to be performed.
_ Practical guidelines
These give practical guidance for applying the method, based on experience and special considerations for applying them to different categories of user (e.g. people with impairments, the young).
_ Further Information
This section provides references to sources for further information.
Methods covered include:
4.1 Brainstorm
4.2 Controlled testing
4.3 Diary keeping
4.4 Focus groups
4.5 Functionality matrix
4.6 Group discussion
4.7 Interviews
4.8 Observation
4.9 Paper prototyping
4.10 Parallel design
4.11 Rapid prototyping
4.12 Scenario building
4.13 Storyboarding
4.14 Survey
4.15 Task analysis
4.16 Task allocation
4.17 Video prototyping
4.18 Walkthrough
4.19 Wizard of Oz prototyping
Relating the Methods to the User Requirements Framework
The following table provides guidance on the selection of methods for use in the main stages of the User Requirements Framework (Part B). Selection is based on a number of factors. These include:
• The phase in the process of specifying user requirements
• The time and effort required to apply the method
• The expertise or skills required
• The equipment or facilities required
• The particular strengths of the method.
Note also that the RESPECT deliverable D6.2 'Requirements specification
and evaluation for user groups with special needs', describes how to
relate some of the above methods to users with impairments and
disabilities (visual, hearing, motor and cognitive), as well as elderly
and young users. The methods covered include: group discussions,
interviews, observation, surveys, controlled testing.
| Characteristics | Applicable to Framework stage: | ||||||
| 1. User context & Early design | 2. Proto- type and User test | 3 User Req Document- ation | Time and Effort required. | Expertise or Skills required. | Equipment Facilities required. | Particular Strengths | |
| Methods | |||||||
| 1. Brainstorm |  |
Low | Group motivater. | Generating ideas | |||
| 2. Controlled testing |
| Medium | Subject handling. Planning. | Quiet area or lab., VCR and camera. | Identifying interaction problems | ||
| 3. Diary keeping | |
Medium | Captures day-to-day usage. | ||||
| 4. Focus group | |
|
Low | Group chairing. | Discuss topic in-depth | ||
| 5. Functionality matrix | |
|
Low | System knowledge | Spreadsheet software | Refining list of functions. | |
| 6. Group discussion | |
|
|
Low | Group chairing. | Airing issues. | |
| 7. Interview | |
Low | Neutral non-leading | Individual opinions in-depth. | |||
| 8. Observation | |
Medium | Event recording. | Seeing real situation | |||
| 9. Paper prototyping | |
Medium | Ability to present and capture ideas. | Quick way to test out ideas for system. | |||
| 10. Parallel design |
| High | Group man -agement | Provides design ideas. | |||
| 11. Rapid prototyping | |
Medium | Openness. Software development | Rapid development software. | Tests outs interactivity of system. | ||
| 12. Scenario building | |
Medium | Group chairing. | Way of testing concept. | |||
| 13. Storyboarding | |
Medium | Group chairing. Drawing. | User appreciati'n of concept. | |||
| 14. Survey | |
High | Survey design and analysis. | Data handling package. | Mass collection of opinion. | ||
| 15. Task analysis | |
Medium | Interview-ing. | Understand-ing current work in depth. | |||
| 16. Task allocation | |
Medium | Interview-ing. | Establishing basis for satisfying jobs. | |||
| 17. Video prototyping | |
High | Editing. Interview-ing | Way of presenting concept realistically | |||
| 18. Walkthrough | |
Medium | Group chairing. | Careful check of system design. | |||
| 19. Wizard of Oz | |
High | Technical. Testing. | Simulation equipment linked together. | Way to testing advanced concepts. | ||
Table 1. Comparison of User Requirements methods